Multi-mode selectable media playback

ABSTRACT

A system includes a computing platform having a hardware processor and a memory storing a software code. The software code is executed to receive a content selection input identifying audio-video (AV) content from a user, and determine a user preferred playback mode for a core video component of the AV content using one or more of (x) a media consumption profile of the user, (y) a playback mode selection input received from the user, or (z) a playback mode supported by a user device. The software code also obtains a media package containing multiple versions of the core video component and metadata identifying a default playback mode, and streams the AV content to the user device using: the user preferred playback mode when a version of the core video component corresponding to the user preferred playback mode is contained in the media package, or the default playback mode otherwise.

BACKGROUND

Audio-video (AV) content has for decades been, and continues to be, oneof the world's most popular mediums for the consumption of entertainmentcontent. As the technology used to produce and display AV content haschanged, so have the playback modes in which that content is presentedto viewers. For instance, black-and-white video gave way to color,standard definition video has largely been replaced by high-definition(HD) and ultra-high-definition (UHD), and the aspect ratio used torender most AV content has largely migrated from 4:3 to 16:9, to name afew examples.

With respect to aspect ratio, at present the majority of consumerdisplays, for example televisions and mobile devices, use a 16:9 HDaspect ratio when rendering video content. As a result, the process ofmaking historical content available on a modern streaming platform mayentail remastering that content to the 16:9 aspect ratio in order toenable a full screen viewing experience. For content originating in anaspect ratio other than 16:9, such as the 4:3 aspect ratio, theremastering process re-frames the content. During re-framing, portionsof the original video frames may be cropped out. For example, whenre-framing content originally created in a 4:3 aspect ratio the top andbottom sections of the frame will typically be cropped out. However, insome instances, removing those portions of the video can undesirablyalter the visual effectiveness of some frames, as well as undermine thecreative intent of the story line, thereby diminishing the viewingexperience of a subscriber to the streaming service.

SUMMARY

There are provided systems and methods for enabling multi-modeselectable media playback, substantially as shown in and described inconnection with at least one of the figures, and as set forth morecompletely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary system for enabling multi-mode selectablemedia playback, according to one implementation;

FIG. 2 shows a diagram including a more detailed exemplaryrepresentation of a user device communicatively coupled to the systemshown in FIG. 1 , according to one implementation;

FIG. 3A shows an exemplary media package suitable for use in enablingmulti-mode selectable media playback, according to one implementation;

FIG. 3B shows an exemplary streamed audio-video content including asubset of the media, assets contained in the exemplary media packageshown in FIG. 3A, according to one implementation;

FIG. 4 shows a more detailed exemplary representation of a graphicaluser interface (GUI) provided by the software code of the system shownin FIG. 1 , according to one implementation; and

FIG. 5 shows a flowchart presenting an exemplary method for enablingmulti-mode selectable media playback, according to one implementation.

DETAILED DESCRIPTION

The following description contains specific information pertaining toimplementations in the present disclosure. One skilled in the art willrecognize that the present disclosure may be implemented in a mannerdifferent from that specifically discussed herein. The drawings in thepresent application and their accompanying detailed description aredirected to merely exemplary implementations. Unless noted otherwise,like or corresponding elements among the figures may be indicated bylike or corresponding reference numerals. Moreover, the drawings andillustrations in the present application are generally not to scale, andare not intended to correspond to actual relative dimensions.

The present application discloses systems and methods for enablingmulti-mode selectable media playback that address and overcome thedrawbacks and deficiencies in the conventional art. The presentaudio-video (AV) content delivery solution advances the state-of-the-artby enabling a user to select among different formatted versions of thesame core video component of AV content to be played back with one ormore media assets shared by each different version of the video. Thepresent application discloses a novel and inventive media packagecontaining the multiple versions of the core video component and mediaassets, such as one or more audio tracks (hereinafter “audio track(s)”),descriptive metadata, subtitles, and artwork, one or more of which maybe shared by the different version of the core video component. As aresult, a user may advantageously select to consume AV content inblack-and-white or in color, in standard definition (SD), highdefinition (HD), or ultra-high-definition (UHD), or AV content includingvideo rendered in a variety of aspect ratios, using media assetscontained in a single media package.

In addition, because media assets such as audio track(s), subtitles,metadata, and artwork may be shareable among multiple versions of thesame core video component of AV content that are packaged together, theentire suite of AV experiences enabled by the same media package mayshare the same unique media identifier, such as the same EntertainmentIdentifier Registry identification (EIDR ID). As a result, the presentAV content delivery solution streamlines and simplifies analyticstracking the content consumption and viewing habits of users, therebymaking it possible for providers of AV content to be more responsive touser preferences.

In some implementations, the systems and methods disclosed by thepresent application may be substantially or fully automated. It is notedthat, as used in the present application, the terms “automation,”“automated,” and “automating” refer to systems and processes that do notrequire the participation of a human system administrator. Although, insome implementations, a human system administrator may review theperformance of the automated systems operating according to theautomated methods described herein, that human involvement is optional.Thus, in some implementations, the methods described in the presentapplication may be performed under the control of hardware processingcomponents of the disclosed automated systems.

It is further noted that, as used in the present application, the term“core video component” refers to a video sequence including the entirevideo portion of a unit of AV content. Consequently, for example, wherethe unit of AV content takes the form of a feature film, the core videocomponent of that AV content includes the entire video portion of thefilm. Analogously, where the unit of AV content takes the form of atelevision (TV) episode, the core video component of that AV contentincludes the entire video portion of the episode. In someimplementations, a core video component may include interstitial contentand advertising content, while in other implementations, one or both ofsuch interstitial content and advertising content may be omitted fromthe core video component. Examples of interstitial content may includepromotional content for the unit of AV content, promotions for other AVcontent, and diversions such as quizzes and games related to the unit ofAV content, to name a few.

It is also noted that at least one of the different versions of the samecore video component stored in a single media package differ from theother versions based on one or more unique video characteristics.Examples of unique video characteristics that may differ among differentcore video components include display format, pixel density or displayresolution, i.e. SD versus HD versus UHD, and dynamic range, i.e. lightand dark contrast range or luminance, to name a few. Moreover, specificexamples of the various display formats that may serve as the uniquevideo characteristic differentiating among different core videocomponents may include aspect ratio, coloration, i.e. black-and-whiteversus color video frames, two-dimensional (2D) versus three-dimensional(3D) video, immersiveness, e.g., virtual reality (VR) video, andproprietary display formats, such as IMAX®, for instance.

Moreover, as defined for the purposes of the present application, theexpression “playback mode” refers to presentation settings of a mediaplayer that correspond to the unique video characteristic of the versionof the core video component being played out by the media player. Thus,a playback mode corresponding to a core video component characterized bya 4:3 aspect ratio would include media player settings to supportdisplay of the video having that aspect ratio, while a playback modecorresponding to a UHD core video component would include media playersettings to support display of video in UHD, and so forth.

It is noted that in many implementations, each version of the core videocomponent contained in the same media package will share the sametimecode and the same audio track(s). However, in some implementations,one or more of the versions of the core video component may be longer orshorter than other versions contained in the same media package, and mayutilize different audio track(s).

FIG. 1 shows an exemplary system for enabling multi-mode selectablemedia playback, according to one implementation. As shown in FIG. 1 ,system 100 includes computing platform 102 having hardware processor 104and system memory 106 implemented as a non-transitory storage device.According to the present exemplary implementation, system memory 106stores playback mode selection software code 110 providing graphicaluser interface (GUI) 120. Moreover, FIG. 1 shows user 140 utilizing oneof user device 130 a including display 136 a or user device 130 bincluding display 136 b to interact with system 100.

As further shown in FIG. 1 , system 100 is implemented within a useenvironment including communication network 108, user profile database112 storing media consumption profile 114 of user 140, and AV contentsource 116. In addition, FIG. 1 shows login input 142, content selectioninput 144, and playback mode selection input 146, as well as mediapackage 150 and AV content 152 streamed to user device 130 a or 130 band including a subset of the media assets contained in media package150 (AV content 152 hereinafter referred to as “streamed AV content152”). Also shown in FIG. 1 are network communication links 118 ofcommunication network 108 interactively connecting system 100 with userprofile database 112, AV content source 116, and user devices 130 a and130 b.

Media package 150 may be stored in system memory 106, and may be used byplayback mode selection software code 110 to provide streamed AV content152 to user 140 via GUI 120. Although the present application refers toplayback mode selection software code 110 and media package 150 as beingstored in system memory 106, more generally, system memory 106 may takethe form of any computer-readable non-transitory storage medium. Theexpression “computer-readable non-transitory storage medium,” as used inthe present application, refers to any medium, excluding a carrier waveor other transitory signal that provides instructions to hardwareprocessor 104 of computing platform 102. Thus, a computer-readablenon-transitory storage medium may correspond to various types of media,such as volatile media and non-volatile media, for example. Volatilemedia may include dynamic memory, such as dynamic random access memory(dynamic RAM), while non-volatile memory may include optical, magnetic,or electrostatic storage devices. Common forms of computer-readablenon-transitory media include, for example, optical discs, RAM,programmable read-only memory (PROM), erasable PROM (EPROM), and FLASHmemory.

Moreover, although FIG. 1 depicts system 100 as including singlecomputing platform 102, that exemplary representation is provided merelyas an aid to conceptual clarity. More generally, system 100 may includeone or more computing platforms 102, such as computer servers forexample, which may be co-located, or may form an interactively linkedbut distributed system, such as a cloud-based system, for instance. As aresult, hardware processor 104 and system memory 106 may correspond todistributed processor and memory resources within system 100. In onesuch implementation, computing platform 102 may correspond to one ormore web servers accessible over a packet-switched network such as theInternet, for example. Alternatively, computing platform 102 maycorrespond to one or more computer servers supporting a wide areanetwork (WAN), a local area network (LAN), or included in another typeof private or limited distribution network.

Although user devices 130 a and 130 b are shown as a smart TV and tabletcomputer, respectively, in FIG. 1 , those representations are alsoprovided merely as an example. More generally, user devices 130 a and130 b may be any suitable mobile or stationary computing devices orsystems that implement data processing capabilities sufficient to enableuse of GUI 120, support connections to communication network 108, andimplement the functionality ascribed to user devices 130 a and 130 bherein. For example, in other implementations, user devices 130 a and130 b may take the form of desktop computers, laptop computers, orsmartphones, for example.

Displays 136 a and 136 b of respective user devices 130 a and 130 b maytake the form of liquid crystal displays (LCDs), light-emitting diode(LED) displays, organic light-emitting diode (OLED) displays, quantumdot (QD) displays, or displays using any other suitable displaytechnology that performs a physical transformation of signals to light.It is noted that, in some implementations, displays 136 a and 136 b maybe integrated with respective user devices 130 a and 130 b, such as whenuser devices 130 a and 130 b take the form of laptop or tablet computersfor example. However, in other implementations, for example where userdevices 130 a and 130 b take the form of a computer tower in combinationwith a desktop monitor, displays 136 a and 136 b may be communicativelycoupled to, but not physically integrated with respective user devices130 a and 130 b.

FIG. 2 shows a more detailed representation of exemplary user device 230in combination with computing platform 202 of system 200, according toone implementation. As shown in FIG. 2 , user device 230 iscommunicatively coupled to computing platform 202 by networkcommunication link 218. Computing platform 202 includes hardwareprocessor 204, transceiver 238 a, and system memory 206 implemented as anon-transitory storage device. As further shown in FIG. 2 , systemmemory 206 contains playback mode selection software code 210 aproviding GUI 220.

User device 230 includes hardware processor 232 and memory 234implemented as a non-transitory storage device storing playback modeselection software code 210 b providing GUI 220, and may store mediaconsumption profile 214 of user 140 in FIG. 1 . As also shown in FIG. 2, user device 230 further includes transceiver 238 b and display 236 forplaying back streamed AV content 252 via GUI 220.

Network communication link 218, and system 200 including computingplatform 202 having hardware processor 204 and system memory 206,correspond respectively in general to network communication link 118,and system 100 including computing platform 102 having hardwareprocessor 104 and system memory 106, in FIG. 1 . Thus, networkcommunication link 218, and system 200 including computing platform 202,hardware processor 204, and system memory 206 may share any of thecharacteristics attributed to respective network communication link 118,and system 100 including computing platform 102, hardware processor 104,and system memory 106 by the present disclosure, and vice versa. As aresult, like system 200, system 100 may include a feature correspondingto transceiver 238 a.

In addition, playback mode selection software code 210 a providing GUI220 corresponds in general to playback mode selection software code 110providing GUI 120, in FIG. 1 . Consequently, playback mode selectionsoftware code 110 and GUI 120 may share any of the characteristicsattributed to respective playback mode selection software code 210 a andGUI 220 by the present disclosure, and vice versa.

Streamed AV content 252, media consumption profile 214 of user 140, anduser device 230 having display 236 correspond respectively in general tostreamed AV content 152, media consumption profile 114, and either orboth of user devices 130 a and 130 b having respective displays 136 aand 136 b, in FIG. 1 , and those corresponding features may share any ofthe characteristics attributed to either corresponding feature by thepresent disclosure. Thus, like user device 230, user devices 130 a and130 b may include features corresponding to hardware processor 232,transceiver 238 b, and memory 234 storing playback mode selectionsoftware code 210 b and media consumption profile 214 of user 140. Inaddition, like displays 136 a and 136 b, display 236 may take the formof an LCD, LED display, OLED display, QD display, or a display using anyother suitable display technology that performs a physicaltransformation of signals to light. Moreover, like user devices 130 aand 130 b, user device 230 may take a variety of forms, such as a smartTV, a smartphone, or a desktop, laptop, or tablet computer, for example.

Transceivers 238 a and 238 b may be implemented as wirelesscommunication hardware and software enabling user device 130 a/130 b/230to exchange data with computing platform 102/202 via networkcommunication link 118/218. For example, transceivers 238 a and 238 bmay be implemented as fourth generation of broadband cellular technology(4G) wireless transceivers, or as 5G wireless transceivers configured tosatisfy the IMT-2020 requirements established by the InternationalTelecommunication Union (ITU).

With respect to playback mode selection software code 210 b, it is notedthat in some implementations, playback mode selection software code 210b may be a thin client application of playback mode selection softwarecode 110/210 a. In those implementations, playback mode selectionsoftware code 210 b may enable user device 130 a/130 b/230 to providelogin input 142, content selection input 144, and playback modeselection input 146, shown in FIG. 1 , to computing platform 102/202 forprocessing, and to receive streamed AV content 152/252 for rendering ondisplay 136 a/136 b/236 via GUI 120/220.

FIG. 3A shows exemplary media package 350 suitable for use in enablingmulti-mode selectable media playback, according to one implementation,while FIG. 3B shows exemplary streamed AV content 352 including a subsetof the media assets contained in media package 350 in FIG. 3A, accordingto one implementation. As shown in FIGS. 3A and 3B, media package 350includes multiple versions 360 a and 360 b of a core video component ofAV content identified by a media identifier, i.e., core video component360 a and core video component 360 b both identified by same media ID362. In addition, media package 350 includes multiple media assetsincluding one or more sets of subtitles 366 (hereinafter “subtitle(s)366”), one or more audio tracks 368 (hereinafter “audio track(s) 368”),descriptive metadata 370, and artwork 372 related to versions 360 a and360 b of the core video component. Also shown in FIGS. 3A and 3B istimecode 364 common to versions 360 a and 360 b of the core videocomponent.

Versions 360 a and 360 b of the core video component of the AV contentidentified by media ID 362 differ from one another by each having atleast one unique video characteristic relative to the other. Accordingto the exemplary implementation shown in FIG. 3A, the unique videocharacteristic distinguishing versions 360 a and 360 b of the core videocomponent from one another is their respective aspect ratio. However, inother implementations, the unique video characteristic distinguishingversions 360 a and 360 b from one another may be different, such astheir respective coloration, pixel density, or dynamic range, forexample. It is noted that although two versions 360 a and 360 b of thecore video component are shown in FIG. 3A in the interests of conceptualclarity, in other implementations, media package 350 may include morethan two versions of the core video component. It is further noted that,in some implementations, versions 360 a and 360 b of the core videocomponent may differ based on more than one video characteristic.

According to the exemplary implementation shown in FIGS. 3A and 3B,because the only difference between versions 360 a and 360 b of the corevideo component is their respective aspect ratio, timecode 364,subtitle(s) 366, audio track(s) 368, descriptive metadata 370, andartwork 372 may be shared by versions 360 a and 360 b. That is to say, asingle instantiation of each of timecode 364, subtitle(s) 366, audiotrack(s) 368, descriptive metadata 370, and artwork 372 may beadvantageously used for playback of all versions of the core videocomponent contained in media package 350.

In other implementations some, but not all of timecode 364, subtitle(s)366, audio track(s) 368, descriptive metadata 370, and artwork 372 maybe shared by versions 360 a and 360 b of the core video component. Forexample, where versions 360 a and 360 b differ based on their respectivecoloration, timecode 364, subtitle(s) 366, audio track(s) 368, anddescriptive metadata 370 may be shared, but not artwork 372.Alternatively, in implementations in which versions 360 a and 360 bdiffer based on their respective pixel density or dynamic range,timecode 364, audio track(s) 368, and descriptive metadata 370 may beshared, but not subtitle(s) 366 or artwork 372. Nevertheless, in allimplementations, each version of the core video component contained inmedia package 350 advantageously shares same media ID 362, which may bean EIDR ID for example.

Streamed AV content 352 includes one of the multiple versions of thecore video component contained in media package 350, as well as othermedia assets to enhance playback of the one version of the core videocomponent. For example, in the implementation shown by FIGS. 3A and 3B,streamed AV content 352 includes version 360 b of the core videocomponent but not version 360 a. Moreover, because according to thepresent implementation, all of timecode 364, subtitle(s) 366, audiotrack(s) 368, descriptive metadata 370, and artwork 372 are shared byversion 360 b of the core video component, those media assets are alsoincluded in streamed AV content 352.

Media package 350 corresponds in general to media package 150 in FIG. 1. Consequently, media package 150 may share any of the characteristicsattributed to corresponding media package 350 by the present disclosure,and vice versa. Thus, like media package 350, media package 150 maycontain multiple versions 360 a and 360 b of the core video componentsharing media ID 362 and timecode 364, as well as shareable media assetsincluding subtitle(s) 366, audio track(s) 368, descriptive metadata 370,and artwork 372, Streamed AV content 352 corresponds in general tostreamed AV content 152/252 in FIGS. 1 and 2 . Consequently, streamed AVcontent 152/252 may share any of the characteristics attributed tostreamed AV content 352 by the present disclosure, and vice versa.

FIG. 4 shows exemplary GUI 420 provided by playback mode selectionsoftware code 110/210 a of system 100/200 or by playback mode selectionsoftware code 210 b of user device 130 a/130 b/230, according to oneimplementation. As shown in FIG. 4 exemplary GUI 420 includes mediaplayer 422 playing back streamed AV content 452. In addition to mediaplayer 422, GUI 420 further includes AV content catalogue 424, “continuewatching” selector 426, “playback mode” selector 428, “up next” playlist462 listing AV content items 454, 456, and 458, and input object 448(shown as an exemplary cursor in FIG. 4 ) usable by user 140, in FIG. 1, to interact with GUI 220.

GUI 420 corresponds in general to GUI 120/220, in FIGS. 1 and 2 . Thatis to say, GUI 120/220 may share any of the characteristics attributedto GUI 420 by the present disclosure, and vice versa. Thus, although notshown in FIGS. 1 and 2 , GUI 120/220 may include media player 422, AVcontent catalogue 424, “continue watching” selector 426, “playback mode”selector 428, “up next” playlist 462, and input object 448. Moreover,streamed AV content 452 corresponds in general to streamed AV content152/252/352 in FIGS. 1, 2, and 3B. Consequently, streamed AV content 452may share any of the characteristics attributed to correspondingstreamed AV content 152/242/352 by the present disclosure, and viceversa. In other words, like streamed AV content 352, streamed AV content452 may include features corresponding to core video component 360 b andshared media assets including timecode 364, subtitle(s) 366, audiotrack(s) 368, descriptive metadata 370, and artwork 372.

The functionality of playback mode selection software code 110/210 a inFIGS. 1 and 2 will be further described by reference to FIG. 5 . FIG. 5shows flowchart 500 presenting an exemplary method for enablingmulti-mode selectable media playback, according to one implementation.With respect to the method outlined by FIG. 5 , it is noted that certaindetails and features have been left out of flowchart 500 in order not toobscure the discussion of the inventive aspects disclosed in the presentapplication. It is further noted that actions 501 and 502 of flowchart500 are described in FIG. 5 as “optional” because in some use cases,user 140 may already have logged in to his or her account with system100/200, and media consumption profile of user 140 may already have beenaccessed in response to that login. Consequently, in someimplementations, the method outlined in FIG. 5 may begin with action 503rather than action 501.

Nevertheless, referring to FIG. 5 in combination with FIGS. 1 and 2 , insome implementations, flowchart 500 can begin with receiving login input142 from user device 130 a/130 b/230 of user 140 (action 501). Forexample, where user 140 is a subscriber to a content streaming service,user 140 would typically have established a user account and logincredentials for accessing that account. Action 501 corresponds tosubmission of login input 142 including those login credentials uniquelyidentifying user 140 to system 100/200. As shown by FIG. 1 , in oneimplementation, login input 142 may be received from user device 130a/130 b/230 of user 140 by system 100 via communication network 108 andnetwork communication links 118. In those implementations, login input142 may be received by playback mode selection software code 110/210 a,executed by hardware processor 104 of computing platform 102.

Continuing to refer to FIGS. 1, 2, and 5 , in some implementations,flowchart 500 can continue with accessing, using login input 142, mediaconsumption profile 114/214 of user 140 (action 502). By way of example,playback mode selection software code 110/210 a may use informationincluded in login input 142 to access media consumption profile 114/214of user 140, which may be stored in user profile database 112, or inmemory 234 of user device 130 a/130 b/230. Media consumption profile114/214 of user 140 may include an AV content consumption history ofuser 140, user devices 130 a/130 b/230 utilized by user 140 to consumeAV content, playback modes preferred by user 140 for playback of AVcontent, and playback modes for playback of AV content that aresupported by each of user devices 130 a/130 b/230. Action 502 may beperformed by playback mode selection software code 110/210 a, executedby hardware processor 104 of computing platform 102.

In various implementations, flowchart 500 can commence or con action503, in which content selection input 144 identifying an AV contentselected by user 140 is received from user device 130 a/130 b/230.Content selection input 144 may identify the AV content selected by user140 by title, by media ID 362 in FIGS. 3A and 3B, or by both the titleand media ID 362, for example. For instance user 140 may supply contentselection input 144 to system 100/200 via GUI 120/220/420, through useof input object 448 in combination with AV content catalogue 424,“continue watching” selector 426, or “up next” playlist 462. As shown byFIG. 1 , content selection input 144 may be received from user device130 a/130 b/230 of user 140 by system 100 via communication network 108and network communication links 118. In such implementations, contentselection input 144 may be received by playback mode selection softwarecode 110/210 a, executed by hardware processor 104 of computing platform102.

Flowchart 500 continues with determining the preferred playback mode ofuser 140 for a core video component of the AV content, whereindetermining the preferred playback mode uses one or more of mediaconsumption profile 114/214 of user 140, playback mode selection input146 received from user device 130 a/130 b/230, or a playback modesupported by user device 130 a/130 b/230 (action 504). The preferredplayback mode determined in action 504 may specify an aspect ratio ofthe core video component of the AV content during playback, thecoloration of that video, its pixel density or resolution, or itsdynamic range, for example. As specific examples, user 140 may prefer SDblack-and-white video playback with 4:3 aspect ratio for playback ofstreamed AV content 152/252/352/452.

In some use cases in which determination of the user preferred playbackmode in action 504 is performed using media consumption profile 114/214of user 140, that determination may be performed based on an AV contentconsumption history of user 140. For example, user 140 may havepreviously watched the AV content identified in action 503 and may havespecified a user preferred playback mode for the AV content at thatearlier time. Alternatively, the AV content identified in action 503 maybe part of a series of episodic content that user 140 has previouslywatched. In those implementations, action 504 may be performed based onthe user preferred playback mode for other episodes in the series. Asyet another alternative, or in addition, action 504 may be performedbased on a user preferred playback mode of user 140 for other AV contentsharing the same genre as the AV content identified in action 503.

However, in some implementations, it may be advantageous or desirable toenable user 140 to manually determine his/her user preferred playbackmode for the AV content identified in action 503. In thoseimplementations, user 140 may utilize input object 448 and “playbackmode” selector 428 of GUI 120/220/420 to provide playback mode selectioninput 146 from user device 130 a/130 b/230. Thus, in some use cases,determination of the user preferred playback mode in action 504 isperformed using playback mode selection input 146 received from userdevice 130 a/130 b/230.

In implementations in which a preferred playback mode of user 140 thatis identified using media consumption profile 114/214 of user 140 orusing playback mode selection input 146 is supported by user device 130a/130 b/230, that preference of user 140 is typically determinative.However, in some implementations, that preferred playback mode may notbe supported by user device 130 a/130 b/230. In those implementations,action 504 may include determining a closest match between a userspecified playback mode and a playback mode supported by user device 130a/130 b/230.

For example, the playback capabilities of user device 130 a/130 b/230may be evaluated, and those capabilities may be used to generate aprioritized list of media attributes that are used to calculate theoptimal playback mode for the AV content through a process calledplayback selection. During playback selection, the current session ofuser 140 may be inspected for user playback preferences, and those userpreferences take priority. Action 504 may be performed by playback modeselection software code 110/210 a, executed by hardware processor 104 ofcomputing platform 102. It is noted that although flowchart 500 listsaction 504 subsequent to action 503, that representation is merelyexemplary. In various implementations, action 504 may follow action 503,may precede action 503, or may be performed substantially concurrentlywith action 503.

Flowchart 500 continues with obtaining media package 150/350 containingmultiple versions 360 a and 360 b of the core video component of the AVcontent and descriptive metadata 370 identifying a default playback modefor the core video component, wherein at least one of versions 360 a and360 b of the core video component has a unique video characteristic(action 505). As shown in FIG. 1 , in some implementations, mediapackage 150/350 may be obtained by system 100 from AV content source116, via communication network 108 and network communication links 118.Media package 150/350 may be obtained by media selection software code110/210 a, executed by hardware processor 104 of computing platform 102.

As noted above by reference to FIG. 3A, in some implementations, theunique video characteristic distinguishing versions 360 a and 360 b ofthe core video component from one another may be their respectivedisplay format, such as their respective aspect ratio, coloration, i.e.black-and-white versus color video frames, whether they include 2D or 3Dvideo, their respective immersiveness, e.g., VR video, or their use of aproprietary display format, such as IMAX®, for example. However and asalso noted above, in other implementations, the unique videocharacteristic distinguishing versions 360 a and 360 b from one anothermay be their respective pixel density or display resolution, i.e. SDversus HD versus UHD, or their respective dynamic range, for example.Moreover, and as further noted above by reference to FIG. 3A, in someimplementations, versions 360 a and 360 b of the core video componentmay differ based on more than one video characteristic.

As also noted above, when a preferred playback mode of user 140 isdetermined using media consumption profile 114/214 of user 140 or usingplayback mode selection input 146, that preference of user 140 istypically controlling. However, in some use cases, user 140 may be a newuser of system 100 without an extensive media consumption profile andmay decline to select a preferred playback mode via GUI 120/220/420.Alternatively, in some use cases, the user preferred playback modedetermined in action 504 may not correspond to any of versions 360 a and360 b of the core video component contained in media package 150/350. Inthose use cases, the default playback mode identified by descriptivemetadata 370 may be utilized to playback the core video component.

According to the exemplary method outlined in FIG. 5 , flowchart 500 cancontinue and conclude with delivering streamed AV content 152/252/352/52to user device 130 a/130 b/260 (action 506). Streaming of streamed AVcontent 152/252/352/452 to user device 130 a/130 b/230 in action 506 maybe performed by media selection software code 120/220 a, executed byhardware processor 104 of computing platform 102, and using the userpreferred playback mode determined in action 504, when versions 360 aand 360 b of the core video component include a version of the corevideo content corresponding to the user preferred playback mode.Alternatively, streaming of streamed AV content 152/252/352/452 to userdevice 130 a/130 b/230 in action 506 may be performed by media selectionsoftware code 120/220 a, executed by hardware processor 104 of computingplatform 102, using the default playback mode identified by descriptivemetadata 370, when versions 360 a and 360 b of the core video componentdo not include the version of the core video content corresponding tothe user preferred playback mode.

Referring to FIGS. 1 and 4 , a significant advantage of the present AVcontent delivery solution is that it allows user preferences to workseamlessly across different user devices 130 a and 130 b, therebyenabling playback-dependent functionality, e.g., AV content accessedusing “continue watching” selector 426, “up next” playlist 462, orcontent launched from a promotional page to carry over from user device130 a or 130 b. For example, AV content having playback initiated onuser device 130 a using a particular playback mode may be paused by user140, and playback may be subsequently be resumed on user device 130 busing the same playback mode automatically.

If user 140 has indicated a preference for a playback mode that does notcorrespond to a version of the core video component contained in mediapackage 150/350, the playback selection process will fall back to thedefault playback mode so that logical story progression and creativeintent can be maintained. User 140 may utilize “playback mode” selector428 of GUI 120/220/420 to change his or her indicated preference asdesired, across multiple sessions and multiple user devices 130 a and130 b, without interrupting the progression of content presentations,e.g., at the episodic, seasonal, or series level. Moreover, in someimplementations, actions 503, 504, 505, and 506 (hereinafter “actions503-506”), or actions 501, 502, and 503-506 may be performed in anautomated process from which participation of a human systemadministrator may be omitted.

Thus, the present application discloses systems and methods for enablingmulti-mode selectable media, playback that address and overcome thedrawbacks and deficiencies in the conventional art. The present AVcontent delivery solution advances the state-of-the-art by enabling auser to select among different versions of the same core video componentof AV content to be played back with one or more media assets shared byeach different version of the video. Furthermore, and as describedabove, the present application discloses a novel and inventive mediapackage containing the multiple versions of the core video component andmedia assets, such as audio tracks, descriptive metadata, subtitles, andartwork that, in various implementations, may be shared by the differentformatted versions of the core video. As a result, a user mayadvantageously select to consume AV content in black-and-white or incolor, in SD, HD, or UHD, or AV content including video rendered in avariety of aspect ratios, using media assets contained in a single mediapackage and collectively identified using a single unique mediaidentifier, such as an EIDR ID.

By reusing shareable media assets such as timecodes, audio tracks,subtitles, artwork and descriptive metadata for multiple viewingexperiences reduces the amount of content to manage, quality control,and cache for optimizing content delivery. A “continue watching”selector of the system provided GUI allows a user to resume viewing ofAV content where she or he has left off, using the same user preferredplayback mode across multiple viewing experiences of the same AVcontent. An “up next” playlist shown via the GUI allows the user topreview what can be watched next (e.g., the next episode of a series)and to enter the viewing experience of that “up next” title whilepreserving the user preferred playback mode. Use of a single mediaidentifier to identify all formatted versions of the same core videocomponent of the AV content advantageously facilitates a user search forcontent, as well as content consumption analytics by an owner of the AVcontent, by returning a single consolidated result for a single title,rather than multiple results for multiple versions of the same title.

From the above description it is manifest that various techniques can beused for implementing the concepts described in the present applicationwithout departing from the scope of those concepts. Moreover, while theconcepts have been described with specific reference to certainimplementations, a person of ordinary skill in the art would recognizethat changes can be made in form and detail without departing from thescope of those concepts. As such, the described implementations are tobe considered in all respects as illustrative and not restrictive. Itshould also be understood that the present application is not limited tothe particular implementations described herein, but manyrearrangements, modifications, and substitutions are possible withoutdeparting from the scope of the present disclosure.

What is claimed is:
 1. A system comprising: a computing platformincluding a hardware processor and a system memory; a software codestored in the system memory; the hardware processor configured toexecute the software code to: receive, from a user device of a user, acontent selection input identifying an audio-video (AV) content selectedby the user; determine a user preferred playback mode for a core videocomponent of the AV content, wherein determining uses at least one of(x) a media consumption profile of the user, (y) a playback modeselection input received from the user device, or (z) a playback modesupported by the user device; obtain a media package containing aplurality of versions of the core video component of the AV content anda metadata identifying a default playback mode for the core videocomponent, wherein at least one of the plurality of versions of the corevideo component has a unique video characteristic; and stream the AVcontent to the user device using: the user preferred playback mode, whenthe plurality of versions of the core video component include a versionof the core video component corresponding to the user preferred playbackmode, or the default playback mode, when the plurality of versions ofthe core video component do not include the version of the core videocomponent corresponding to the user preferred playback mode.
 2. Thesystem of claim 1, wherein the hardware processor is further configuredto execute the software code to: receive a login input from the userdevice of the user; and access, using the login input, the mediaconsumption profile of the user.
 3. The system of claim 1, wherein eachof the plurality of versions of the core video component share a samemedia identifier.
 4. The system of claim 3, wherein the same mediaidentifier comprises an Entertainment Identifier Registry identification(EIDR ID).
 5. The system of claim 1, wherein the plurality of versionsof the core video component share a same timecode and a same audio trackincluded in the media package.
 6. The system of claim 1, wherein theplurality of versions of the core video component share a samedescriptive metadata and a same set of subtitles included in the mediapackage.
 7. The system of claim 1, wherein the unique videocharacteristic of the at least one of the plurality of versions of thecore video component comprises at least one of an aspect ratio, acoloration, a pixel density, or a dynamic range of the at least oneversion of the core video component.
 8. A method for use by a systemincluding a computing platform having a hardware processor and a systemmemory storing a software code, the method comprising: receiving from auser device of a user, by the software code executed by the hardwareprocessor, a content selection input identifying an audio-video (AV)content selected by the user; determining, by the software code executedby the hardware processor, a user preferred playback mode for a corevideo component of the AV content, wherein determining uses at least oneof (x) a media consumption profile of the user, (y) a playback modeselection input received from the user device, or (z) a playback modesupported by the user device; obtaining, by the software code executedby the hardware processor, a media package containing a plurality ofversions of the core video component of the AV content and a metadataidentifying a default playback mode for the core video component,wherein at least one of the plurality of versions of the core videocomponent has a unique video characteristic; and streaming, by thesoftware code executed by the hardware processor, the AV content to theuser device using: the user preferred playback mode, when the pluralityof versions of the core video component include a version of the corevideo component corresponding to the user preferred playback mode, orthe default playback mode, when the plurality of versions of the corevideo component do not include the version of the core video componentcorresponding to the user preferred playback mode.
 9. The method ofclaim 8, further comprising: receiving, by the software code executed bythe hardware processor, a login input from the user device of the user;and accessing, by the software code executed by the hardware processorand using the login input, the media consumption profile of the user.10. The method of claim 8, wherein each of the plurality of versions ofthe core video component share a same media identifier.
 11. The methodof claim 10, wherein the same media identifier comprises anEntertainment Identifier Registry identification (EIDR ID).
 12. Themethod of claim 8, wherein the plurality of versions of the core videocomponent share a same timecode and a same audio track included in themedia package.
 13. The method of claim 8, wherein the plurality ofversions of the core video component share a same descriptive metadataand a same set of subtitles included in the media package.
 14. Themethod of claim 8, wherein the unique video characteristic of the atleast one of the plurality of versions of the core video componentcomprises at least one of an aspect ratio, a coloration, a pixeldensity, or a dynamic range of the at least one version of the corevideo component.
 15. A computer-readable non-transitory storage mediumhaving a media package enabling media playback selection stored thereon,the media package comprising: an audio-video (AV) content including aplurality of versions of a core video component, each one of theplurality of versions of the core video component having a differentaspect ratio than another one of the plurality of versions of the corevideo component; a metadata identifying a default playback mode of thecore video component, the default playback mode corresponding to one ofthe plurality of versions of the core video component; and at least onemedia content asset shared by the plurality of versions of the corevideo component; wherein the plurality of core video components share asame media identifier.
 16. The computer-readable non-transitory storagemedium of claim 15, wherein the same media identifier comprises anEntertainment Identifier Registry identification (EIDR ID).
 17. Thecomputer-readable non-transitory storage medium of claim 15, wherein theat least one media content asset shared by the plurality of versions ofthe core video component comprise a same timecode and a same audio trackincluded in the media package.
 18. The computer-readable non-transitorystorage medium of claim 15, wherein the at least one media content assetshared by the plurality of versions of the core video component comprisea same descriptive metadata and a same set of subtitles included in themedia package.
 19. The computer-readable non-transitory storage mediumof claim 15, wherein each one of the plurality of versions of the corevideo component has a different dynamic range than another one of theplurality of versions of the core video component.
 20. Thecomputer-readable non-transitory storage medium of claim 15, whereineach one of the plurality of versions of the core video component has adifferent pixel density than another one of the plurality of versions ofthe core video component.